Skip to content

feat: Support flashinfer.rmsnorm #3424

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 18, 2025
Merged

feat: Support flashinfer.rmsnorm #3424

merged 1 commit into from
Apr 18, 2025

Conversation

bowang007
Copy link
Collaborator

This PR resolves some issues and support flashinfer.rmsnorm

Checklist:

  • My code follows the style guidelines of this project (You can use the linters)
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas and hacks
  • I have made corresponding changes to the documentation
  • I have added tests to verify my fix or my feature
  • New and existing unit tests pass locally with my changes
  • I have added the relevant labels to my PR in so that relevant reviewers are notified

@github-actions github-actions bot added component: tests Issues re: Tests component: conversion Issues re: Conversion stage component: api [Python] Issues re: Python API component: dynamo Issues relating to the `torch.compile` or `torch._dynamo.export` paths labels Mar 4, 2025
@github-actions github-actions bot requested a review from peri044 March 4, 2025 07:41
github-actions[bot]

This comment was marked as outdated.

@bowang007 bowang007 marked this pull request as draft March 4, 2025 07:41
@bowang007 bowang007 self-assigned this Mar 4, 2025
@bowang007 bowang007 marked this pull request as ready for review March 4, 2025 20:34
@bowang007 bowang007 changed the title test: Support flashinfer.rmsnorm feat: Support flashinfer.rmsnorm Mar 4, 2025
@narendasan
Copy link
Collaborator

@bowang007 Can you move the auto plugin gen tests to a runner other than the one used for converter tests?

Copy link
Collaborator

@zewenli98 zewenli98 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like flashiner-python installation is problematic on CI. After resolving this issue, can you also check if this works for python 3.13 because we are going to support 3.13 as of 2.7 release while some packages may not be available for 3.13.

@bowang007
Copy link
Collaborator Author

bowang007 commented Apr 17, 2025

It looks like flashiner-python installation is problematic on CI. After resolving this issue, can you also check if this works for python 3.13 because we are going to support 3.13 as of 2.7 release while some packages may not be available for 3.13.

@zewenli98 I think this is expected since in the official doc it says it supports until python 3.12 here: https://docs.flashinfer.ai/installation.html

@bowang007 bowang007 force-pushed the flashinfer_rmsnorm branch from aed7cb1 to 85d7b25 Compare April 17, 2025 23:20
@bowang007
Copy link
Collaborator Author

bowang007 commented Apr 17, 2025

It looks like flashiner-python installation is problematic on CI. After resolving this issue, can you also check if this works for python 3.13 because we are going to support 3.13 as of 2.7 release while some packages may not be available for 3.13.

I updated the requirements.txt to get the python3.13 restriction @zewenli98

Copy link
Collaborator

@narendasan narendasan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Collaborator

@zewenli98 zewenli98 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I saw some CI errors, not sure if that's related. I restarted the failed jobs. If they pass then LGTM

@bowang007 bowang007 force-pushed the flashinfer_rmsnorm branch from 85d7b25 to 00ddd55 Compare April 18, 2025 21:05
@github-actions github-actions bot removed component: conversion Issues re: Conversion stage component: dynamo Issues relating to the `torch.compile` or `torch._dynamo.export` paths labels Apr 18, 2025
@bowang007 bowang007 merged commit 5e38c04 into main Apr 18, 2025
38 of 41 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants